3 . A special contract creation transaction is used to deploy on the

Ethereum platform.

4. The special contract creation address 0× 0 identifies this sent

transaction.

5 . A function of the originating account and nonce is each contract

creation transaction identified and derived by an Ethereum address.

6. The recipient sending funds to the contract or calling one of the

contract’s functions can use the Ethereum address in a transaction.

7 . A transaction initiated from an EOA called by a transaction enables all

smart contracts to ultimately get executed in Ethereum Contracts.

8. The first contract in the chain of execution always is called by a

transaction from an EOA, and subsequently, contracts call each other

one by one.

9 . It is not possible for contracts to run “on their own” or “in the

background”.

10. U ntil a transaction triggers execution, the contracts lie dormant either

directly or indirectly as part of a chain of contract calls.

11. The smart contracts are not executed “in parallel” as the Ethereum

world computer is a single-threaded machine.

Smart contract transaction rules

The smart contract transaction rules specify that:

1. A contract’s code cannot be changed.

2. A contract can be “deleted”, leaving an account blank, as there is no

longer any code there to execute,

3 . After the contract has been deleted, any transaction sent to that

account address does not result in any code execution,

4. Execute the EVM opcode SELFDESTRU CT to delete a contract

costing “negative gas”, a gas refund, an incentive for the release of

network client resources.

5 . The blockchain being immutable, the deletion of a contract does not

remove its transaction history.